The 640 MEG Shareware Studio 2

home *** CD-ROM | disk | FTP | other *** search

/ The 640 MEG Shareware Studio 2 / The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO / pcb / pcbfv33.zip / PCBFV.DOC < prev next >

Wrap

Text File | 1993-01-29 | 95KB | 1,896 lines

------------------------------------------------------------------ | | | | | | | | | PCBFV Version 3.3 | | | | PCBoard F V Compressed File Viewer | | | | For | | | | PCBoard Versions 14.5 & 14.5a | | | | including | | | | PCBoard /M Multi-Port | | | | | | * Seamless Interface - Looks Like Part of PCBoard * | | | | | | Allows Text File Reading On-Line | | | | | | Allows Selecting Files For Individual Download | | | | | | Runs In The F V Shell, As A Door, In PCBFiler, and Locally | | | | | | | | All Options Are Sysop-Configurable | | | | | | | | PCBFV Version 3.3 | | | | (C) Copyright 1990-1993 Yandell Computer Services | | | | 12121 Little Road - Bldg. 303 - Suite 212 | | Hudson, FL 34667 | | | | DATA -- (813) 842-8099 | | | | | | January 29, 1993 | | | | | | | ------------------------------------------------------------------ -------------------------------------------------------------------- PCBFV -------------------------------------------------------------------- TABLE OF CONTENTS INTRODUCTION Page ------------ ---- 1.0 What Is PCBFV 3 1.1 What Is New In Version 3.3 3 1.2 Multi-Nodes, Networks, Multi-taskers 3 1.3 Documentation Definition - (F) versus (FLAG) 3 INSTALLING PCBFV IN THE F_V SHELL --------------------------------- 2.0 PCBFV's SWAP and Determining Memory Requirements 4 2.1 Setting Up PCBVIEW.BAT 4 2.2 Multi-Node Systems and PCBFV.CNF 5 2.3 Upgrading from Previous Versions to PCBFV 3.3 5 2.4 Running FVSETUP and Creating PCBFV.CNF 6-11 2.5 FVHLP Help File (Macros, Color, Etc.) 12 2.6 Limiting (F)lag File Types with FLAG.DAT 12 2.7 PCBFV's Menu (FVMNU) 13 2.8 Managing Caller Created Compressed Files 13 2.9 Setting up Environment Variables for ZIP 2.0 14 2.10 Sample Configurations 15-16 INSTALLING PCBFV IN OTHER AREAS ------------------------------- 3.0 Installing PCBFV in PCBFiler 17 3.1 Installing PCBFV as a Local Utility 17 3.2 Installing PCBFV as a Door 18 RUN-TIME CONSIDERATIONS ----------------------- 4.0 Notes Regarding the (R)ead Command 19 4.1 Notes Regarding the (S)elect Command 20 4.2 Notes Regarding the (F)lag Command 20 4.3 Notes Regarding the AutoFlag Feature 21 4.4 Notes Regarding "Flagging Across Files" 22 4.5 Notes Regarding the (I)nventory Command 22 4.6 Notes Regarding Compression Utilities 23 4.7 Notes Regarding the (D)elete Command 24 4.8 Notes Regarding the (Z)ip-Extra Command 24 MISCELLANEOUS ------------- 5.0 Sysop Function Keys 25 5.1 Technical Notes 25 5.2 Caller Log Entries 26 5.3 Error Messages 26 5.4 Where to Receive Assistance 27 5.5 Disclaimer and Warranty 27 5.6 License to use PCBFV 27 5.7 New Compression Utility Releases 28 5.8 Revision History 28 REGISTRATION ------------ 6.0 Registering PCBFV 29 6.1 Register with CONFIDENCE - Author Information 29 -------------------------------------------------------------------- Page 3 PCBFV Page 3 -------------------------------------------------------------------- 1.0 What is PCBFV ------------------ PCBFV is a PCBoard BBS utility primarily for use in the F V (File View) shell process. PCBFV may also be used as the file viewer in PCBFiler. PCBFV may be installed to run as a door. PCBFV displays the contents of ZIP, ARJ, LZH, PAK, and ARC files. Self-extracting files created by PKZIP, LHA, and ARJ (2.20 and later) are supported. PCBFV will also display the resolution of .GIF files (width-height- colors). PCBFV will optionally allow a caller to (R)ead text files contained within a compressed file, and search for text within those files. The Sysop may allow the caller to read non-text files in a HEX mode display. PCBFV will also optionally allow a caller to (F)lag a compressed file's members for individual downloading. Uncompressed files in a download path may be read by PCBFV. The Sysop has full control over which features of PCBFV are enabled on their system. The goal in PCBFV's development has been to make the caller's interface to the F V process appear as "seamless" as possible. Great emphasis has been placed on making the appearance of PCBFV appear as similar as possible to PCBoard. 1.1 What is new in version 3.3 ------------------------------- Please read the enclosed FEATURES.NEW file for details. 1.2 Multi-nodes, networks, multi-taskers ----------------------------------------- PCBFV has been developed in a networked environment. All multi-node features are thoroughly tested on our own multi-node PCBoard system. Two of PCBFV's primary beta test facilities are twenty node systems. The largest known installation of PCBFV is on a 225 node system (which is also a beta test site). PCBFV is DESQview aware. It is automatically detected, screen and keyboard I/O are "well behaved", and time slices are given back to other applications while PCBFV is idle at an input prompt. DESQview is the only multi-tasking software supported by PCBFV. Pertinent multi-node information is highlighted with *MULTI-NODE* throughout this document. 1.3 Documentation definition - (F) versus (FLAG) ------------------------------------------------- If "FL", "FLA" or "FLAG" are entered at the PCBFV prompt, the entire compressed file being viewed will be entered into PCBoard's FLAG queue upon return to PCBoard (14.5a). An "F" alone is for extraction of individual files for downloading. Since the "FLAG" command requires no setup or configuration, all references to (F)lag, Flag, Flagging, etc. in this documentation are references to the "F" individual file extraction command process. -------------------------------------------------------------------- Page 4 PCBFV Page 4 -------------------------------------------------------------------- 2.0 PCBFV's SWAP and determining memory requirements ----------------------------------------------------- PCBFV can swap itself to EMS or disk (disk if EMS is not available) if there is insufficient memory to call upon external compression utilities. "Swapping" must be turned on using FVSETUP.EXE. Use the table below to determine if you need to turn swapping on. The memory amounts below are what must be showing on PCBFV's status line in order for the corresponding compression type to function. This column shows the minimum This column shows the minimum memory needed for (R)eading memory needed for creating a FROM the compressed file type. caller's Flag file. PCBFV'S PCBFV'S PCBFV'S PCBFV'S SWAP ON SWAP OFF SWAP ON SWAP OFF 15K 115K < ZIP > 95K 195K 10K 105K < ARC > 40K 140K 55K 155K < LZH > 100K 200K 85K 185K < PAK > 85K 185K 90K 190K < ARJ > 150K 250K NOTES: * If you are running PCBoard in /SWAP mode, it is very unlikely that PCBFV itself would ever need to swap. * If PCBFV swaps and EMS is not available, a disk file is created in the PCBFV work area called FVSWPxxx.$$$ (xxx = node number). 2.1 Setting up PCBVIEW.BAT --------------------------- The first line of your PCBVIEW.BAT file(s) should be ECHO OFF or @ECHO OFF, depending on the version of DOS you are using. Load PCBVIEW.BAT into a text editor. The syntax for calling PCBFV is out- lined in figure 2.1 below. NOTE: Never change drives or CD\ in PCBVIEW.BAT. ALWAYS call PCBFV with its location in-line as shown below. ------------------------------------------------------------------ | M:\PCBFV\PCBFV.EXE PCBFV.CNF %1 | | ------------------ --------- -- | | | | |-> PCBoard will replace this with| | | | the compressed file's name. | | | | | | | ---------> The name of the configuration | | | file. Enter a file NAME only. | | | NEVER place a location with name.| | | *MULTI-NODE* see section 2.2 for | | | more information. | | | | | -------> The executable file name. You MUST place its | | location in-line as shown above if you are not | | putting PCBFV.EXE in each node's \PCB root. | ------------------------------------------------------------------ ---- Figure 2.1 ---- -------------------------------------------------------------------- Page 5 PCBFV Page 5 -------------------------------------------------------------------- 2.2 Multi-Node systems and PCBFV.CNF ------------------------------------- To use a single PCBFV.CNF (providing you are using one PCBFV.EXE) for all nodes, simply use the @NODE@ macro in two of the FVSETUP parameters. These are "work location of extracted file" and "Loc\name of new (F)lagged file". Otherwise, you will have to create a separate .CNF file for each node and feed PCBFV the individual node's .CNF file in each node's PCBVIEW.BAT. Refer to the "sample configurations section" (section 2.10 page 15) and the section on "Running FVSETUP and Creating PCBFV.CNF" section 2.4 page 6 thru 11. 2.3 Upgrading from previous versions to PCBFV 3.3 -------------------------------------------------- *** Upgrading to 3.3 from 3.0 through 3.2 *** --------------------------------------------- REVIEW FEATURES.NEW. The enclosed FVHLP and FVMNU files include new commands since versions 3.0 and 3.1. *** Upgrading to 3.3 from 2.0 through 2.5 *** --------------------------------------------- Use the new FVMNU (menu) and FVHLP (help) files, or rename your old files to these new names. Refer to FEATURES.NEW for more details. Be sure to add the new commands if you are renaming your old FVMNU and FVHLP files to use with PCBFV 3.3. Refer to the enclosed FEATURES.NEW file for new features which you may wish to take advantage of. Set all parameters in FVSETUP with a blinking asterisk (*). This indicates that the parameter has not been set in your PCBFV.CNF. The FVSETUP program will place these asterisks at all parameters which are not set in PCBFV.CNF files from version 2.0 through version 2.5. Create any multi-language FVMNU and FVHLP files you wish to use. If you are using PCBFV in PCBFILER or as a LOCAL UTILITY: If your PCBFV.CNF contains @NODE@ in the "work location of extracted file" parameter, you will have to create a new .CNF file (FILER.CNF for instance) for these uses. The parameters which contained the @NODE@ macros now need to be fully specified in the special FILER.CNF file, and PCBFV.CNF will need to be replaced by FILER.CNF in PCBFILER and any LOCAL UTILITY batch files. **** Upgrading to 3.3 from 1.1 and earlier *** ---------------------------------------------- If you are upgrading from version 1.0 or 1.1 you must completely install a new PCBFV configuration. PCBFV has simply progressed too far and experienced too many enhancements to attempt to upgrade it from these earlier versions. The enclosed FVSETUP.EXE now has F1 help at each configuration parameter, which should enable you to install PCBFV version 3.3 in a matter of minutes. -------------------------------------------------------------------- Page 6 PCBFV Page 6 -------------------------------------------------------------------- 2.4 Running FVSETUP and creating PCBFV.CNF ------------------------------------------- Enclosed with PCBFV 3.3 is a file called FVSETUP.EXE. This file allows you to easily and quickly configure your PCBFV configuration files. If you run a single node system simply use the PCBFV.CNF file which came with PCBFV and modify it using FVSETUP to your needs. If you run a *MULTI-NODE* installation, you will need to decide if you are going to use a different .CNF file for each node or if you are going to use one .CNF file with @NODE@ macros. To start FVSETUP.EXE, enter FVSETUP PCBFV.CNF at your DOS prompt (PCBFV.CNF would be the appropriate node's .CNF file). Each parameter in FVSETUP is described on the following pages. * Idle keyboard time-out (minutes) (and why there is one in PCBFV) ------------------------------------------------------------------ Allows the Sysop to set a keyboard time-out independent of PCBoard. If a caller has abandoned their terminal, a time-out will occur in PCBFV and return them to PCBoard. PCBoard's timer will then start. If you have a large time-out set in PCBoard, it might be a good idea to set a lower one in PCBFV. If the caller is not coming back to the terminal, they will have the combined PCBFV and PCBoard time-outs occur before PCBoard drops them. * Maximum extracted file size ----------------------------- The maximum uncompressed file size allowed to be extracted for BOTH (R)ead & (F)lag commands. If the file selected inside a compressed file's size is larger than what you specify, it cannot be (R)ead NOR (F)lagged for download. You may enter 0 for no limit, however this is not recommended if a RAM drive is used for the `work location of extracted file' parameter (below). This setting is ignored when PCBFV is running in any local mode, or when the Sysop (the name in record #1 of your USERS file) is on remotely. * Work location of extracted file --------------------------------- A "work" location of extracted files for both the (R)ead and (F)lag commands. Whenever a caller (R)eads or (F)lags a file, that file is extracted to the location you specify here. If you have a lot of RAM drive space, it is the ideal place for this parameter. In a *MULTI- NODE* environment, you MUST specify a different "work" directory for each node and indicate that node's directory here. If you are *MULTI-NODE* and are using the single PCBFV.CNF method, place the @NODE@ macro in-line here (C:\WORK@NODE@\). PCBFV never deletes work directories. It simply insures the appropriate work directory exists each time it is run, and creates it if not. If you nest your work subdirectories, PCBFV will only try to create the "last" directory in the nest. For example, if your work location is C:\PCB\PCBFV\WORK then PCBFV will only attempt to create \WORK. IF C:\PCB\PCBFV didn't exist, PCBFV will report it couldn't make the work directory. In these cases, you will need to create the work locations manually. Section 2.4 continues on the next page -------------------------------------------------------------------- Page 7 PCBFV Page 7 -------------------------------------------------------------------- 2.4 Running FVSETUP and creating PCBFV.CNF (continued) ------------------------------------------------------- * Path to compression utilities ------------------------------- Enter ONLY the path of your compression utilities. Do NOT enter a file name in this parameter. This parameter allows PCBFV to go directly to your compression utilities, rather than search your path for them. This results in faster overall extraction/compression response time. DO NOT ENTER A FILE NAME in this parameter. PCBFV will expect to find the following compression utilities: See section 4.6 on page 23 for required compression utilities. * Swap PCBFV if needed ---------------------- PCBFV can swap itself to EMS or disk (disk if EMS is not available) if there is not enough memory available to perform (R)ead or (F)lag functions. These are general guidelines for this setting: Answer (N)o to never SWAP, (Y)es to automatically determine if EMS is available and SWAP to it if so or SWAP to disk if not, or (D)isk to force PCBFV to SWAP to disk even if EMS is available. (1) If you are running PCBoard in /SWAP mode, PCBFV will most likely always have enough memory for (R)ead and (F)lag operations. (2) If this setting is answered Yes, PCBFV will only swap if needed. This usually occurs in extremely limited memory situations and/or if PCBoard is not running in the /SWAP mode, and/or when LZH, PAK, or ARJ files are being (R)ead or (F)lagged from. (3) Never answer Yes to this setting if using a multi-tasker other than those listed as being supported in section 1.2 on page 3. * Follow eXpert mode in USERS ----------------------------- Answering NO will force PCBFV to always display FVMNU unless it is turned off with the PCBFV X command. Answering YES will force PCBFV to follow the caller's mode as it was last set in the USERS file. * Disable (R)ead text option ---------------------------- Allows the Sysop to disable the (R)ead text function of PCBFV. If disabled, the (R) command should be removed from FVHLP and FVMNU. * Security needed to (R)ead files --------------------------------- Enter the minimum security level needed for a caller to be able to read text in a compressed file. Sysops may want to prohibit new callers, non-subscribing callers, etc. from using this feature. Section 2.4 continues on the next page -------------------------------------------------------------------- Page 8 PCBFV Page 8 -------------------------------------------------------------------- 2.4 Running FVSETUP and creating PCBFV.CNF (continued) ------------------------------------------------------- * Maximum lines to read per file -------------------------------- Enter 0 for no limit, or a limit up 9999. This will limit the number of lines in EACH text file a caller can read. Some Sysops would rather caller's not read entire text files on-line. Less scrupulous callers might use the (R)ead function to screen cap text files and avoid file or byte download ratios which may be in effect. When setting this, remember that some authors don't get around to describing what their software does until 10 or 20 pages (screens) into the documentation. Between 400 and 500 is a good MINIMUM limit. This limitation does not apply to non-text files being displayed in HEX mode (if allowed - see section 2.4 page 11). This setting is ignored when PCBFV is running in any local mode, or when the Sysop (the name in record #1 of your USERS file) is on remotely. * Default wildcard (R)ead answer -------------------------------- This parameter allows you to set what the default answer will be when the caller is requesting files to (R)ead. To present the regular (R)ead input prompt without a default answer, leave this field BLANK, or enter NONE. To present a default answer at the read input prompt, such as *.DOC enter *.DOC in this parameter. This will display: File within PCBFV.ZIP to read,(L)ist,(wildcards are OK)? (*.DOC ) You MUST include a wildcard (* or ?) if enabling a default answer. Any caller input other than (Enter) will cause PCBFV to erase the default and allow the caller to enter their own input. * Y/N/A prompt for wildcard find -------------------------------- You may specify PART of the Yes/No/Abort prompt which appears for each filename that matches a wildcard (R)ead request. Because so many different suggestions have been received as to what this prompt should be, it was decided to allow each Sysop to configure it to their needs. Note: the (Y) added to the end of the prompt will always appear, since Yes is the default answer. (Next: PCBFV.DOC Size: 37793) (H)elp, Read this file? (Y) |_____________________| | What you place in this parameter will be inserted here. Suggestions: (H)elp, Read this file? (H)elp, Read this file (Yes,No,Abort)? (H)elp, Read this file (Enter)=Yes? Section 2.4 continues on the next page -------------------------------------------------------------------- Page 9 PCBFV Page 9 -------------------------------------------------------------------- 2.4 Running FVSETUP and creating PCBFV.CNF (continued) ------------------------------------------------------- * Disable (S)elect file option ------------------------------ Allows the Sysop to disable the "(S)elect another compressed file" option. You may allow the caller the ability to select another compressed file for viewing without exiting the F V shell (or without returning from PCBFV if used as a door). (S)elect improves the caller interface to the file view process, since the caller is not returned back and forth to PCBoard if they have several files to view. The (S)elect command uses PCBoard conference DLPATH.LST files. The (S)elect command uses PCBoard's FSEC to determine if a caller has security to view a file. PCBFV will also ask the caller for the password if a file is password protected in FSEC. The details of this function are explained in detail in section 4.1 on page 20 of this document. This feature may not be available on some PCBoard /D and /S single node systems running PCBoard 14.5 if SHARE is loaded (see page 25 section 5.1). * # files in each (F)lagged file -------------------------------- Allows the Sysop to specify the number of files (1-99) that can be added to the file which contains each individually flagged file. Entering 0 (zero) disables the (F)lag function. If (F)lag is disabled, the (F) and (I) commands should be removed from FVHLP and FVMNU. * Security needed to (F)lag files --------------------------------- Enter the minimum security level needed for a caller to be able to (F)lag separate files within compressed files for downloading. Sysops may want to prohibit new callers, non-subscribing callers, etc. from using this feature. This feature may not be available on some PCBoard /D and /S single node systems running PCBoard 14.5 if SHARE is loaded (see page 25 section 5.1). Section 2.4 continues on the next page -------------------------------------------------------------------- Page 10 PCBFV Page 10 -------------------------------------------------------------------- 2.4 Running FVSETUP and creating PCBFV.CNF (continued) ------------------------------------------------------- * Loc\Name of new (F)lagged file -------------------------------- If (F)lag is allowed, enter the location AND name of the file which will be created and will contain the individual files the caller selects for downloading. The location MUST be a drive and path which are listed in your DLPATH.LST!!! The .EXT you place on the filename determines the compression method used by PCBFV to create the file. In a *MULTI-NODE* environment, the file NAME in the above parameter MUST be different for each of your nodes. You may accomplish this by either placing a different name in each node's .CNF file, or if you are using a single PCBFV.CNF then place the @NODE@ macro in-line here (C:\UPLOAD\FLAG-@NODE@.ZIP). IMPORTANT: The location you specify should be in DLPATH.LST, and should NOT be located in a PCBoard 14.5a INDEX file. If the (F)lag option is disabled, this entry may be blanked out. * Disable (F)lagging across files --------------------------------- Callers may flag files from different compressed files without having to download the flagged file after each file view. You may disable this feature. This feature is explained in detail in section 4.4 on page 22 of this document. * Disable AutoFlag on PCB return -------------------------------- When PCBFV terminates the F V session and returns control to PCBoard, it will prompt PCBoard to place the caller created flagged file into PCBoard's own FLAG list (if the caller has flagged separate files in PCBFV). This parameter allows you to disable this feature. Refer to section 4.3 on page 21 for details on "AutoFlag". * Your PCBFV registration number -------------------------------- This is the registration number received when PCBFV is registered. All functions are enabled in unregistered copies. The only limitation is that while reading files, remote callers will not have access to the (F)ind command. (F)ind may be used in unregistered copies by the Sysop from remote as well as in all local modes for evaluation purposes. Registration also removes the PCBFV [UNREGISTERED COPY] message and brief delay at program termination. This is not replaced with your system's name or any other text. This provides a true, seamless, "looks like PCBoard" process. See the ORDER.FRM file for details. Section 2.4 continues on the next page -------------------------------------------------------------------- Page 11 PCBFV Page 11 -------------------------------------------------------------------- 2.4 Running FVSETUP and creating PCBFV.CNF (continued) ------------------------------------------------------- * Non-Text file type for HEX mode --------------------------------- PCBFV has the ability for callers to read Non-Text files located in compressed files, if the Sysop chooses. There are different methods in how this may be implemented: (N)one, never display Non-Text files. Selecting this mode disallows Non-Text files from ever being displayed. This is like turning the HEX display mode off completely. Callers will receive a "cannot read non-text file" message if they try to read a non-text file. (E)xclude executable and compressed files. Any file with a filename extension of EXE, COM, ZIP, GIF, LZH, PAK, ARC, and ZOO cannot be read by the caller. Any other file names will be displayed to the caller in a HEX display mode if PCBFV determines the file is not a text file. (A)ll, any non-text file will be displayed to the caller in HEX mode if PCBFV determines the file is not a text file. The (E)xclude mode is probably the best. This gives callers the ability to view things like dBase, Lotus, and other data files while preventing them from looking at executables and "zips in zips" in HEX mode. Since PCBFV allows reading of files in a download path, this setting will also determine how non-text files in download paths are handled regarding the non-text HEX mode display. * Main prompt ------------- You may change PCBFV's main command prompt. If your PCBoard prompts are significantly changed, PCBFV actually won't live up to its "looks like part of PCBoard" claim unless this prompt is changed also. The default "(H)elp, File View Command?" is supplied. You may want to to insert the command letters or command abbreviations: (H)elp, L, R, S, F, FLAG, I, C, B, X, Z, P, View Command? Valid PCBFV commands are (H)elp, (L)ist, (R)ead, (S)elect, (F)lag, (I)nventory, (C)RC, (B)rief, (Z)ip-extra, (X)pert, (P)rogram info, and FLAG. It is recommended you at least stay with the PCBoard convention of beginning the prompt with (H)elp. Don't include any command letters if they are disabled in your configuration of PCBFV. -------------------------------------------------------------------- Page 12 PCBFV Page 12 -------------------------------------------------------------------- 2.5 FVHLP help file (macros, color, etc.) ------------------------------------------ FVHLP is a very important part of PCBFV. It is very likely that every caller will want (H)elp, at least the first time they use PCBFV. There are four very important @macros@ used by FVHLP. @FILENAME@ - Whenever this appears in FVHLP, PCBFV will replace it with the file name which is currently being viewed. @FILENAMEPD@ - Same as @FILENAME@ except padded to twelve spaces. @FLAGFILE@ - Whenever this appears in FVHLP, PCBFV will replace it with the name of the compressed file which will be created when a caller Flags files for separate download. This feature is especially helpful for *MULTI-NODE* systems, since a different compressed file name is mandatory for each node. @FLAGFILE@ will be replaced by that node's file name as it appears in that node's .CNF file, thereby creating the need for only one help file. @FLAGFILEPD@ - Same as @FLAGFILE@ except padded to twelve spaces. Color is used in FVHLP by utilizing the same color macros used in PCBoard 14.5. ANSI capabilities have been intentionally omitted. Review FVHLP and remove any commands which are not enabled. FVHLP must reside in the same location with PCBFV.EXE. 2.6 Limiting (F)lag file types with FLAG.DAT --------------------------------------------- You may limit (F)lagging activity to certain types of files. With a text editor, create a file called FLAG.DAT in the same location with PCBFV.EXE. Simply begin entering COMPLETE or WILDCARD file names of those files which you wish the caller to be able to flag. Press enter (RETURN) after each name so that each entry is on a new line. If FLAG.DAT is not present, no limitations are placed on Flag names. See figure 2.6 below for examples of names in FLAG.DAT. ------------------------------------------------------------------ | Good examples Bad examples | | ------------- ------------ | | *.DOC PCBFV uses regular DOS .DOC | | *.TXT wildcard specs to see if .TXT | | READ*.* a file is a match. If so, READ | | *.NEW the file may be flagged. .NEW | | FILE.CFG FILE* | ------------------------------------------------------------------ ---- Figure 2.6 ---- If a caller attempts to flag a file which is not allowed, they will be shown the types of file names which can be flagged. FLAG.DAT must reside in the same location with PCBFV.EXE -------------------------------------------------------------------- Page 13 PCBFV Page 13 -------------------------------------------------------------------- 2.7 PCBFV's menu (FVMNU) ------------------------- The Sysop may create a "menu" which will be displayed before PCBFV's command prompt each time the prompt is displayed. This should be a simple text file called "FVMNU" and may contain PCBoard style color macros and PCBFV's four custom macros (see FVHLP). This file must reside in the same location with PCBFV.EXE. If this file does not exist, PCBFV simply shows its main prompt. PCBFV's main prompt may be customized if the Sysop does not wish to use a menu. 2.8 Managing caller created compressed files --------------------------------------------- Each time PCBFV runs it checks for the presence of a caller created flagged file. If the file exists and the Sysop has DISABLED the "Flag across files" function, the file will be deleted. If "Flag across files" is allowed, an information file (created by PCBFV, explained in detail in section 4.5 page 22) is checked to see if the same caller executing the view is the same caller who created the current flagged file. If so, the flagged file is kept for additional flagging, if not, the caller created flagged file is deleted. **** Deleting FLAGGED files when a caller logs off (PCBoard 14.5a): Create or modify $$LOGOFF.BAT in a path available to all nodes or in each node's root to include: if exist d:\down\flagged.zip del d:\down\flagged.zip Replace d:\down\flagged.zip with the appropriate information for each node. ****Deleting FLAGGED files when a caller logs off (PCBoard 14.5): Set PCBoard to "Exit to DOS after each call". This is done with PCBSETUP, selection F (Options 1) from the PCBSETUP main menu. Answer Yes to the "Exit to DOS after each call" setting. Modify BOARD.BAT as indicated below: @echo off if exist remote.bat rename remote.bat remote.sys if exist event.bat rename event.bat event.sys if exist door.bat del door.bat if exist endpcb del endpcb PCB145 if exist remote.bat remote if exist door.bat door if exist event.bat event if errorlevel == 5 goto cycle < INSERT HERE if exist endpcb goto end :cycle < INSERT HERE if exist d:\down\flagged.zip del d:\down\flagged.zip < INSERT HERE board :end cls Replace d:\down\flagged.zip with the appropriate location and name of the flagged file for the node whose BOARD.BAT is being modified. -------------------------------------------------------------------- Page 14 PCBFV Page 14 -------------------------------------------------------------------- 2.9 Setting up environment variables for ZIP 2.0 ------------------------------------------------- PKZIP 2.0 performs several auto-sensing functions. These include the detection and use of EMS, XMS, 386, Novell, DPMI, and more. If it is necessary for you to disable use of these auto-sensed modes while using these utilities with PCBFV, it may be done using ENVIRONMENT VARIABLES. These unique PCBFV environment variables should only be used if these auto-sensing functions need to be turned off while being used by PCBFV. If these auto-sensing functions are turned off permanently using prescribed methods in the ZIP manual, these PCBFV variables will not be needed. You may set the command line equivalents in the following PCBFV environment variables. These variables are added to the command line PCBFV creates when calling the ZIP utilities for the (R)ead and (F)lag functions. Variable Affects Command Allowable switches -------------------------------------------------------------------- FVUNZIP PKUNZIP.EXE (R)ead -+ (No EMS use) -- (No XMS use) -3 (No 386 instructions) -) (No DPMI) FVZIP PKZIP.EXE (F)lag -+ (No EMS use) -- (No XMS use) -3 (No 386 instructions) -) (No DPMI) -~ (No Novell) -( (Use slow memcopy 486 only) You should set these environment variables in each node's AUTOEXEC.BAT which requires them when using PKZIP and\or PKUNZIP with PCBFV. These variables will NOT function properly if set in the PCBVIEW.BAT file that calls PCBFV.EXE. Examples: SET FVZIP=-+ would turn off EMS use in PKZIP when Flagging files. SET FVZIP=--+ same as above, plus XMS is turned off. SET FVUNZIP=-) turns off DPMI use in PKUNZIP when Reading files. NOTE: The FVUNZIP environment variable is not needed if the same functions are permanently turned off with the PKUNZIP environment variable as outlined in the PKZIP 2.04e manual addendum. NOTE: The FVZIP environment variable is not needed if the same functions are being permanently turned off with the PKZIP.CFG configuration file as outlined in the PKZIP 2.04e manual. NOTE: Only the characters in the chart above may be used in these two PCBFV environment variables. PCBFV will not use ANY of the variable's contents if other switches are attempted. NOTE: The use of these environment variables in no way affects the amount of memory PCBFV will test for with each function. -------------------------------------------------------------------- Page 15 PCBFV Page 15 -------------------------------------------------------------------- 2.10 Sample configurations --------------------------- [Single node] ------------- C:\PCB ------ PCBVIEW.BAT - contains PCBFV.EXE PCBFV.CNF %1 PCBFV.EXE PCBFV.CNF FVHLP, FVMNU, & FVZRO You may prefer this alternate single node configuration C:\PCBFV (or the location of your choice) -------- PCBFV.EXE PCBFV.CNF FVHLP, FVMNU, & FVZRO C:\PCB ------ PCBVIEW.BAT - contains C:\PCBFV\PCBFV.EXE PCBFV.CNF %1 [*MULTI-NODE*] ------------------------------------------------------------- [Example 1 (using a single PCBFV.CNF file)] Your multi-node PCBFV.CNF would look something like this: Idle keyboard time-out (minutes) : 3 Maximum extracted file size : 600000 Work location of extracted file : C:\WORK@NODE@\ Path to compression utilities : C:\UTILS\ Swap PCBFV if needed (Y,D,N) : N Follow eXpert mode in USERS : N Disable (R)ead text option : N Security needed to (R)ead files : 0 Maximum lines to (R)ead per file : 0 Default wildcard (R)ead answer : NONE Y/n/a prompt for wildcard find : (H)elp, Read this file? Disable (S)elect file option : N # files in each (F)lagged file : 10 Security needed to (F)lag files : 0 Loc\Name of new (F)lagged file : C:\UPLOAD\FLAG@NODE@.ZIP Disable (F)lagging across files : N Disable AutoFlag on PCB return : N Non-Text file type for HEX mode : E Your PCBFV registration number : 0 Main prompt : (H)elp, File View Command? ONLY edit PCBFV.CNF files with the enclosed FVSETUP utility. Section 2.10 continues on the next page -------------------------------------------------------------------- Page 16 PCBFV Page 16 -------------------------------------------------------------------- 2.10 Sample configurations (continued) --------------------------------------- If you cannot use the single file PCBFV.CNF method you will need to make a configuration file for each node and place the different configuration file name in each node's PCBVIEW.BAT. [Sample - node 1 (using separate PCBFVx.CNF files)] Idle keyboard time-out (minutes) : 3 Maximum extracted file size : 600000 Work location of extracted file : C:\WORK1\ Path to compression utilities : C:\UTILS\ Swap PCBFV if needed (Y,D,N) : N Follow eXpert mode in USERS : N Disable (R)ead text option : N Security needed to (R)ead files : 0 Maximum lines to (R)ead per file : 0 Default wildcard (R)ead answer : NONE Y/n/a prompt for wildcard find : (H)elp, Read this file? Disable (S)elect file option : N # files in each (F)lagged file : 10 Security needed to (F)lag files : 0 Loc\Name of new (F)lagged files : C:\UPLOAD\FLAG1.ZIP Disable (F)lagging across files : N Disable AutoFlag on PCB return : N Non-Text file type for HEX mode : E Your PCBFV registration number : 0 Main prompt : (H)elp, File View Command? [Sample - node 2 (using separate PCBFVx.CNF files)] Idle keyboard time-out (minutes) : 3 Maximum extracted file size : 600000 Work location of extracted file : C:\WORK2\ Path to compression utilities : C:\UTILS\ Swap PCBFV if needed (Y,D,N) : N Follow eXpert mode in USERS : N Disable (R)ead text option : N Security needed to (R)ead files : 0 Maximum lines to (R)ead per file : 0 Default wildcard (R)ead answer : NONE Y/n/a prompt for wildcard find : (H)elp, Read this file? Disable (S)elect file option : N # files in each (F)lagged file : 10 Security needed to (F)lag files : 0 Loc\Name of new (F)lagged file : C:\UPLOAD\FLAG2.ZIP Disable (F)lagging across files : N Disable AutoFlag on PCB return : N Non-Text file type for HEX mode : E Your PCBFV registration number : 0 Main prompt : (H)elp, File View Command? ONLY edit PCBFV.CNF files with the enclosed FVSETUP utility. As demonstrated, PCBFV is very flexible in how it may be installed. It can be installed in all configurations of PCBoard. -------------------------------------------------------------------- Page 17 PCBFV Page 17 -------------------------------------------------------------------- 3.0 Installing PCBFV in PCBFiler --------------------------------- Enclosed with PCBFV version 3.3 is a new utility, FVMM, which is designed to bring many capabilities to PCBFiler's ALT-V process that have not been available before. Review FVMM.DOC. If you decide you do not want to install FVMM in PCBFiler, the instructions below will assist you in installing PCBFV in PCBFiler instead. A /L parameter is used (see below) which instructs PCBFV to operate in a "true" local mode. All "on-line" functions are disabled, such as keyboard time-out, caller status line at the bottom of the screen, etc. The local monitor type is automatically detected and color is used if appropriate. Special Note: If you are installing PCBFV in PCBFiler and are using PCBFV.CNF files with the @NODE@ macro in the "work location of extracted file" parameter in FVSETUP, you must create a special configuration file for use in the /L mode which fully specifies the "work location". You may call this file FILER.CNF and install it with PCBFV into PCBFiler as shown below. At PCBFiler's first screen select "Edit PCBFILER defaults page 2". At the bottom of this screen, enter parameters as follow: File VIEWERS - filename extensions and commands for executing viewer File Extension : ZIP DOS Command : c:\pcb\PCBFV FILER.CNF /L File Extension : ARJ DOS Command : c:\pcb\PCBFV FILER.CNF /L File Extension : GIF DOS Command : c:\pcb\PCBFV FILER.CNF /L For each compression type (which PCBFV is compatible with) place the "DOS Command :" entry as above. The parameters must be placed in the same order as they are shown in the examples: Name\location of PCBFV.EXE, configuration file, then /L. The (S)elect command and all function keys are disabled in this mode. All other sections in this documentation apply to installing PCBFV in PCBFiler. 3.1 Installing PCBFV as a local utility ---------------------------------------- Create a batch file called FV.BAT (or whatever name you choose): C:\PCB\PCBFV PCBFV.CNF /L %1 Place FV.BAT (or whatever you name it) in your DOS path, and you have a full powered viewer, extractor at your fingertips at all times by typing FV FILENAME.ZIP (an extension IS required in this mode). All other areas of this manual apply to this installation. Special Note: If you are installing PCBFV as a local utility and are using PCBFV.CNF files with the @NODE@ macro in "work location of extracted file, you must create a special configuration file for use in the /L mode which fully specifies the "work location". It is recommended that this file be called LOCAL.CNF and installed with PCBFV into FV.BAT instead of PCBFV.CNF as shown above. -------------------------------------------------------------------- Page 18 PCBFV Page 18 -------------------------------------------------------------------- 3.2 Installing PCBFV as a door ------------------------------- This capability exists in case Sysops have a need to diversify the utilization of PCBFV's many features, or in case there is a limited memory situation and PCBoard and PCBFV cannot be allowed to swap. We have heard from many Sysops saying they installed PCBFV as a private door for themselves and\or their Co-Sysops, free of the limitations they wanted PCBFV to impose on regular callers while using the F V process. The documentation for installing PCBFV as a door is almost the same as installing it in the F V shell. For door installation, simply follow the instructions below INSTEAD of those found in section 2.1. All other sections apply to door installation. Install a door called FV in DOOR.LST file with PCBSETUP. Place this entry at the end of DOOR.LST, as the recommended usage calls for invoking PCBFV as a door by name (FV), rather than the conventional way of placing it in your door menu and calling it by number. Answer NO to the USERS.SYS and DOOR.SYS parameters. If using PCBoard 14.5a, it is up to the Sysop to decide on whether to install PCBFV as a "shell to" door or not. Create a door (batch) file called FV : @echo off M:\PCBFV\PCBFV.EXE PCBFV.CNF C:\PCB /DOOR board --------- ------ ----- | | |_ Put PCBFV into door mode | | | |__Location of THIS node's PCB root | |__ PCBFV configuration file. Notice that we didn't change drive and/or cd\ to the PCBFV location. Instead, we called it directly from where FV is run because of PCBFV's ability to do this. This results in faster load time. If, however, you are running *MULTI-NODES* and each node is residing on a different drive, you may find it faster to install PCBFV as a door on each node's drive. Make sure your PCBoard menus reflect the FV command instead of F V. PCBFV (as a door) can be passed a filename from the PCBoard command prompt, the same way the F V shell process passes a file, for example "FV TEST.ZIP". This requires no extra installation by the Sysop and is handled automatically by PCBoard and PCBFV. PCBFV's door mode works with PCBoard 14.5a's "shell to" door mode. If running PCBFV as a "shell to" door in PCBoard 14.5a, do NOT end the door file with the "board" command as shown above. -------------------------------------------------------------------- Page 19 PCBFV Page 19 -------------------------------------------------------------------- 4.0 Notes regarding the (R)ead command ----------------------------------------- In previous versions of PCBFV, only text files could be displayed to the caller. With the addition of the HEX mode display in PCBFV 2.2, the caller may read any type of file, depending on how the Sysop has enabled the HEX mode display feature. Typically, files which contain carriage-return and\or line-feed sequences will be regarded as text files by PCBFV. All other files will have to meet the criteria the Sysop has set for the HEX display feature (see section 2.4 page 11). The (F)ind Text command available while reading text files is a full featured search mechanism. The whole page surrounding the text is displayed with the found text highlighted in the center line of the screen. The "maximum number of lines to display" setting is honored, callers cannot (F)ind past the number of lines the Sysop may have set for this parameter. The (F)ind command is complimented by a (R)epeat Find, which repeats the last Find command performed on the current text. The "maximum number of lines to display" setting is honored, callers cannot (R)epeat past the number of lines the Sysop may have set for this parameter. The text reading (and searching) process is further enhanced by the following commands which allow easy reading of text files: (T)op of file command which allows the caller to quickly return to the beginning of the file being read. (P)ageUp allows the previous page of text to be displayed. (<) and (>) scroll the screen left and right for viewing long lines of text (longer than 79 characters) on the screen. The (F)ind, (R)epeat, (P)ageUp. (<), (>), and (T)op commands appear in the "More" prompt at the end of a full page of text. The (R)epeat command only appears after a (F)ind has been executed. When using PCBFV in local mode, the Sysop may use the corresponding cursor movement keys: Home=(T)op PgUp=(P)ageUp PgDn=[Enter], and the left and right arrows = (<) and (>). The (F)ind command is PCBFV's only limited function in unregistered copies. The (F)ind command IS functional in unregistered copies of PCBFV, but only when the Sysop (the name in record #1 of the USERS file) is the person on-line, or when PCBFV is being used in any local mode. PCBFV will read DOS and non-DOS text files. Non-DOS text files are text files which contain line-feeds only, as opposed to DOS files which contain carriage-returns and line-feeds. PCBFV tests text files for characters such as ANSI escape sequences and form feeds. If either are found PCBFV suppresses them before displaying the text. -------------------------------------------------------------------- Page 20 PCBFV Page 20 -------------------------------------------------------------------- 4.1 Notes regarding the (S)elect command ----------------------------------------- PCBFV's (S)elect command is completely conference DLPATH.LST aware. The caller will only be able to (S)elect files to view which are available to the conference they are in (or last in, if using PCBFV as a door). PCBFV's (S)elect command is also completely FSEC aware. When a (S)elect request is found, PCBFV checks FSEC to insure the caller has security to view the file. If the file is password protected, PCBFV will also ask the caller the password, and performs this operation in the same manner as PCBoard. PCBFV uses the "Filename EXTENSION for compressed files" entry in PCBSETUP as the default filename extension when performing its own file searches. PCBFV's (S)elect command is compatible with the new file index system introduced in PCBoard version 14.5a. 4.2 Notes regarding the (F)lag command --------------------------------------- The System Administrator/Operator may specify the type of files the caller may flag (see section 2.6 FLAG.DAT). A security level may be attached to this command. Callers may "flag across files" (see section 4.4 below). There is an (I)nventory command, and the inventory information file is automatically included in each caller created file. Files which are (F)lagged for individual download are automatically placed in the compressed file designated for the node the caller is on. The extracted member is then deleted from the work directory. This keeps the amount of disk space PCBFV is requiring down and allows a RAM drive to be used as a work location, which greatly speeds up overall execution of the F V function. Regardless of how PCBFV is installed, the caller will never be able to include ALL of the files from a compressed file into their caller created file. In all cases, the caller at best will be able to include all but ONE file into their flagged file. For instance, if you set PCBFV to allow 5 files for inclusion into the caller created file, and the caller is viewing a compressed file with 4 files, the most they will be able to flag of those is 3 of the 4. The theory behind this is the caller should download the actual file rather than flagging each individual file. A caller cannot (F)lag a file if they don't have enough daily bytes to download it in PCBoard. This prevents them from going through the motions of Flagging, then returning to PCBoard only to discover they cannot download it anyway. Files which are FREE/NOTIME are EXEMPT from this (F)lag limitation. PCBFV uses the "daily bytes downloaded" as last updated in the USERS file, and the amount of bytes available as installed in FSEC, for this purpose. To bypass this byte check, add /NOBYTE to the end of the PCBFV command line. -------------------------------------------------------------------- Page 21 PCBFV Page 21 -------------------------------------------------------------------- 4.3 Notes regarding the AutoFlag feature ----------------------------------------- If allowed, PCBFV will make PCBoard think the caller has entered instructions to "FLAG" the caller created flagged file as part of PCBoard's own "FLAG" list. PCBoard will remind the caller of the existence of their "flagged" file in the "batch" when the caller enters "D" from PCBoard, logs off without downloading their batch list, etc. How it works: For the purposes of this example, we'll say the name of the caller created file in PCBFV is called FLAGGED.ZIP. PCBFV uses PCBoard 14.5a's PCBSTUFF.KBD file feature to tell PCBoard to enter FLAG FLAGGED.ZIP at the PCBoard prompt after a F V session. Operational notes: If "flagging across files" and AutoFlag are both enabled and it is the first F V session, AutoFlag will occur. On subsequent F V sessions, if the caller Flags (in PCBFV) separate files, they will be asked if they've downloaded FLAGGED.ZIP yet (since/if you allow flagging across files, PCBFV has no way of knowing). If they answer Yes, PCBFV will AutoFlag again at the end of the current F V session. If they answer No, PCBFV won't perform AutoFlag. If the caller answers No, and they really have downloaded FLAGGED.ZIP, then AutoFlag won't occur (since they answered No) and the file will not be placed in PCBoard's FLAG list. Subsequently, if the caller answers Yes they downloaded FLAGGED.ZIP but really didn't PCBFV will AutoFlag the caller created (FLAGGED.ZIP) file. Since the the caller really didn't download (in this scenario) it will still exist in PCBoard's FLAG batch list, and the caller will receive: (@OPTEXT@) duplicates a file already in the batch! This is record #554 in PCBTEXT. Changing it to something like: (@OPTEXT@) exists in the batch list... is recommended as it sounds less like an error message, and is still informative if the caller DBs or FLAGs a duplicate d/l file from PCBoard. The @optext@ in the above examples is replaced with the appropriate caller created flagged file name (FLAGGED.ZIP, etc.). The download path(s) which contain your FLAGGED.ZIP (or FLAG1.ZIP FLAG2.ZIP etc.) should be placed at the beginning of DLPATH.LST so PCBoard's FLAG search occurs as quickly as possible when returning from the F V shell. Do not place this path in PCBoard 14.5a's INDEX. The Auto-Flag feature, introduced in PCBFV 2.1, is no longer compatible with PCBoard 14.5. Auto-Flag now works with PCBoard 14.5a only. -------------------------------------------------------------------- Page 22 PCBFV Page 22 -------------------------------------------------------------------- 4.4 Notes regarding "flagging across files" -------------------------------------------- If you allow the caller to "flag across files", this means they will be able to view a compressed file, select files from it to download individually, then view another compressed file and select individual files from it, adding all of the individual files to one caller created file for downloading. The number which you place in the "# files in each (F)lagged file" parameter in FVSETUP will be observed, even when flagging across files is allowed. If a caller should select an individual filename which is identical in two different compressed files, the caller will be given the choice of which one to keep in the "caller created compressed file", as obviously a compressed file cannot contain two files with the same name. For systems that enforce download file counts, you need to be aware that if you allow "flagging across files" and you also place a high number in the "# of files in each (F)lagged file" parameter in FVSETUP, unscrupulous callers might be able to use it to "beat the system". In most cases, placing a low number in the FVSETUP field "# of files in each (F)lagged file" will prevent this undesirable effect. Also, using FLAG.DAT (see section 2.6) to limit the types of names of files that can be flagged, in conjunction with a low number allowed in each caller created file, will surely thwart this activity. In all cases, disabling "flagging across files" will eliminate the need for concern completely. 4.5 Notes regarding the (I)nventory command -------------------------------------------- This command allows the caller to take inventory of their current "Flag file". They will be shown the contents which will consist of a list of the individual files they have flagged, the compressed file name which the individual files came from, and the size in bytes of the "Flag file" they have created. The file containing the information shown by the (I) command is created by PCBFV in each node's work directory you have assigned it. This file is also automatically included in the "Flag file" the caller will download, so that the caller will have a reference as to which individual files came from which compressed files. The (I)nventory command is disabled if the (F)lag command is disabled. -------------------------------------------------------------------- Page 23 PCBFV Page 23 -------------------------------------------------------------------- 4.6 Notes regarding compression utilities ------------------------------------------ The compression utilities required by PCBFV depend on the types of compressed files carried on your system. Below is a summary of the required files for each compression type, and any limitations PCBFV imposes on them. All compression utilities must reside in the location specified for "Location of Compression Utilities" in PCBFV.CNF using FVSETUP.EXE. (SFX = Self-Extracting) * ZIP and ZIP SFX (.EXE) files ------------------------------ PKUNZIP.EXE version 2.04e is required for reading and flagging from ZIP files. If flagging is allowed and the caller created file is a ZIP file (FLAG.ZIP etc.) then PKZIP.EXE version 2.04e is required. * LZH and LZH SFX (.EXE & .COM) files ------------------------------------- LHA.EXE version 2.12 is required for reading and flagging from LZH files. The same file is required if flagging is allowed and the caller created file is a LZH file (FLAG.LZH etc.). * ARJ and ARJ SFX (.EXE) files ------------------------------ ARJ.EXE version 2.30 is required for reading and flagging from ARJ files. Because ARJ SFX files did not contain an ARJ signature prior to ARJ version 2.20, PCBFV will only perform operations on SFX type ARJ files created with ARJ version 2.20 and later. ARJ.EXE is also required if flagging is allowed and the caller created file is an ARJ file (FLAG.ARJ etc.). Sysops using ARJ as a flag file should be aware that a large amount of memory is required to create ARJ files. * PAK files ----------- PAK.EXE version 2.10 is required for reading and flagging from PAK files. The same file is required if flagging is allowed and the caller created file is a PAK file (FLAG.PAK etc.). PAK version 2.10 is not the newest version of PAK. Versions of PAK after 2.10 require far too much memory to use with PCBFV. This older version of PAK is available on the YCS support system if needed. SFX PAK files are not supported by PCBFV. * ARC files ----------- PKUNPAK.EXE version 3.61 is required for reading and flagging from ARC files. If flagging is allowed and the caller created file is an ARC file (FLAG.ARC etc.) then PKPAK.EXE version 3.61 is required. SFX ARC files are not supported by PCBFV. * SDN files ----------- SDN (Shareware Distribution Network) files are PAK files with the .SDN extension. See "PAK files" above for details. -------------------------------------------------------------------- Page 24 PCBFV Page 24 -------------------------------------------------------------------- 4.7 Notes regarding the (D)elete command ----------------------------------------- The (D) command allows the local Sysop to delete unwanted files from ZIP files (only), such as BBS advertisements, COMMAND.COM, etc. This command can only be used if PCBFV has been started with /L on the PCBFV command line such as in PCBFiler, FVMM, or local utility mode. This command is completely disabled whenever a caller is on remotely including the Sysop. If (D) is entered while on-line, it is not accepted as input (in other words, the D cannot even be typed at the PCBFV prompt). After selecting (D), the local Sysop will be prompted for a filename in the compressed file to delete. PCBFV will then re-display the filename and ask the local Sysop for confirmation. If the local Sysop enters a (D) command while viewing a ZIP file which contains ANY files with -AV stamps, PCBFV will warn the Sysop that the ZIP *MIGHT* be an -AV file and will prompt the local Sysop on whether to continue or not. Currently, PCBFV only checks for -AV markings in ZIP files made with PKZIP version 1.10, 2.04c and 2.04e. If a newer version of PKZIP becomes available and is used to create a ZIP and the (D) command is used, PCBFV *MAY* warn that a new compression type has been detected and the -AV test could not be performed. See page 28 section 5.7 for additional details regarding new utilities. Other compression types (non ZIP) may contain "security envelopes". Future versions of PCBFV may be given the ability to detect these "envelopes", thereby allowing the (D) command to function with other compression types in addition to ZIP files. The (D)elete command has the same memory and external compression utility requirements as those listed for ZIP (F)lag requirements. 4.8 Notes regarding the (Z)ip-Extra command -------------------------------------------- PCBFV will display extra technical information about a ZIP file. This extra information includes whether or not member files contain -AV authenticity stamps, the version of PKZip used to compress the member file, whether each member file is text or binary, and the host operating system each file in the ZIP was compressed in (DOS, Amiga, Unix, etc.). NOTE: PCBFV does not check the validity of the -AV stamps, it only displays which files contain them. NOTE: Currently, PCBFV only checks for -AV markings in ZIP files made with PKZIP versions 1.10, 2.04c and 2.04e. If a newer version of PKZIP becomes available and is used to create the file being viewed and the (Z) command is used, the "ZIP -AV" column will be blank or may contain incorrect information. See section 5.7 on page 28 for more details regarding new compression utilities. -------------------------------------------------------------------- Page 25 PCBFV Page 25 -------------------------------------------------------------------- 5.0 Sysop function keys ------------------------ PCBFV follows F3 (printer on/off), F7 (alarm on/off) and F9 (display on/off) toggles from PCBoard. If F3 is on, PCBFV will print any information sent to the caller log to the printer also. If F7 is on, PCBFV will beep locally (usually caller input errors). If F9 is off, PCBFV will turn the screen off. Pressing any key locally turns the screen on if F9 is active. You may toggle these three function keys on or off. Their status will be displayed on the command line in parenthesis (PAB). Note: toggling an option on or off is local to the PCBFV process only, since PCBoard does not read PCBOARD.SYS when returning from a File View. When PCBFV returns control to PCBoard, the toggles will be in the same state as before the File View shell. Note: the B displayed in (PAB) is the F4 page bell indicator. This is shown on PCBFV's status line for information purposes only (if page was allowed in PCBoard before the File View). 5.1 Technical notes -------------------- PCBFV has been designed to run specifically with PCBoard versions 14.5 and 14.5a. PCBFV will not run with earlier versions of PCBoard or with other brands of software. PCBFV automatically detects PCBoard /M multi-port software and switches to FOSSIL communications mode for use with that version of PCBoard's communication driver. Carrier is monitored by PCBFV. Should a caller drop carrier while in PCBFV they will be returned to PCBoard, which will detect the "no carrier" status and cycle appropriately. PCBFV works with non-standard com ports, addresses, and IRQs. COM1 is address 3F8/IRQ 4. COM2 is address 2F8/IRQ 3. If a COM port other than 1 or 2 is used, PCBFV will use the address and IRQ as indicated in PCBOARD.DAT for the node. PCBFV checks for adequate disk space before attempting to extract a file for (R)eading or (F)lagging. If a file name is stored with a directory location in a compressed file, that file cannot be (R)ead or (F)lagged by PCBFV. PCBFV follows the screen color and intensity as set in PCBSETUP for PCBoard (local screen). If using PCBoard 14.5 (not 14.5a) /D or /S single node software and SHARE is loaded, it is impossible for PCBFV to determine the user's security level. Limiting the (R)ead and (F)lag functions based on security is not possible. The (S)elect command is also unavailable. All of the enclosed executable files have been compressed with a commercial compression utility. Uncompressed versions of these files are not available. -------------------------------------------------------------------- Page 26 PCBFV Page 26 -------------------------------------------------------------------- 5.2 Caller log entries ----------------------- PCBFV makes pertinent entries into the caller log as outlined below. If the (F)lag command is enabled, PCBFV will make the following entry in the caller log when a file is flagged: FILENAME.DOC in FILENAME.ZIP flagged for download PCBFV will make the following entries in the caller log to alert the Sysop if inadequate disk space is encountered: Insufficient disk space to Read FILENAME.TXT Insufficient disk space to Flag FILENAME.TXT If the (S)elect command is enabled, PCBFV will make the following entries in the caller log if the corresponding event occurs: View executed on file (FILENAME.ZIP) Error executing View of file (FILENAME.ZIP) (FILENAME.ZIP) not found! Insufficient security for Viewing (FILENAME.ZIP) Incorrect View Password for File (FILENAME.ZIP) (123456789.ZI) is an invalid filename! The caller log entries for the (S)elect command are identical to the corresponding default entries in PCBoard's PCBTEXT. If you do not wish for PCBFV to make these entries to your caller log file(s), add /NOCALLER to the end of the PCBFV command line in your PCBVIEW.BAT file(s). 5.3 Error messages ------------------- PCBFV gives verbose installation error messages, such as invalid paths and file names you may have placed in PCBFV.CNF. These messages appear and there is a short pause while they are displayed. PCBoard erases the local screen after a F V shell and this short pause will allow you to see the message. The following are explanations of PCBFV's run time error messages: * Error extracting file (1) * This means that the file selected for (R)eading or (F)lagging already existed in the work directory designated for this node. As a safety precaution, PCBFV will not overwrite a file which already exists in a work directory. * Error extracting file (2) * This indicates the file appears in the compressed file, but for some reason the extraction utility could not extract it. This could possibly mean PCBFV was unable to find the extraction utility needed. This could also indicate there was insufficient memory available for the extraction process. * bad command or filename * This is a DOS error message indicating that PCBVIEW.BAT could not find PCBFV.EXE, or PCBFV.EXE could not find the appropriate extraction utility. -------------------------------------------------------------------- Page 27 PCBFV Page 27 -------------------------------------------------------------------- 5.4 Where to receive assistance -------------------------------- Yandell Computer Services (YCS) provides the following technical assistance for PCBFV: 813-842-8099 The YCS Support System. Available to all BBS Sysops. INSTANT on-line credit card registration and support system for YCS Shareware. On-line 7 days per week, 24 hours per day. 5.5 Disclaimer and warranty ---------------------------- PCBFV is a shareware product. PCBFV may be uploaded to BBS systems as long as copyright notices are not removed and no changes are made to the program. There are no warranties, expressed or implied, for unregistered copies of PCBFV. Sysops who install PCBFV on their systems assume any and all liabilities for anything which may result as a consequence of running PCBFV. For registered copies of PCBFV, Yandell Computer Services warrants that PCBFV will perform as described in this documentation. In the event that PCBFV does not perform as specified, then Yandell Computer Services may elect to fix PCBFV or refund the amount paid, if notified within 30 days of registration. Under no circumstances shall Yandell Computer Services or the author of PCBFV be liable for any loss of profit or any other damages, including but not limited to special, incidental, consequential, or other damages, arising out of the use or inability to use PCBFV. 5.6 License to use PCBFV ------------------------- PCBFV is not "public domain" or "free" software. A limited license is granted to use and evaluate PCBFV for thirty days after initial installation. PCBFV must be registered if it is used after the initial thirty day evaluation period. A PCBFV registration may be used only on the original licensee's BBS system and only on nodes the original licensee owns and operates for their own purposes. If the original licensee leases or sells some or all of their nodes to another entity, those nodes will require their own PCBFV registration. PCBFV registrations are not transferable. A PCBFV registration is a license to use PCBFV software on one (1) BBS System at a single location with as many nodes as the original licensee owns and operates at THAT location. When the licensee owns and operates other BBS' in other locations, each location requires a separate PCBFV registration. If PCBFV has not been registered after 30 days, a Sysop reminder will begin appearing at program termination and will also be written to the current node's caller log file. -------------------------------------------------------------------- Page 28 PCBFV Page 28 -------------------------------------------------------------------- 5.7 New compression utility releases ------------------------------------- PCBFV generally does not become obsolete when a compression utility adds a new compression method to their line-up. If the author of a particular compression utility adds a new compression type, they usually do not change the "headers" in the compressed file. This allows utilities such as PCBFV to view their contents as normal, except for the "compression method", until PCBFV can be updated. PCBFV will display "New\Unk" for the compression method if viewing a file which was created with a compression utility which contains a new compression type. It is recommended that new compression utilities (versions newer than those listed in section 4.6 page 23) NOT be used for PCBFV's (R)ead, (F)lag, etc. commands without checking with Yandell Computer Services first. Newer compression utility releases can and most likely will require more memory than their predecessors, and PCBFV may need to be updated to test for the correct memory requirements. NOTE: PKZIP -AV stamps have changed with each new release of PKZIP since being added to ZIP version 1.1. Any PCBFV functions utilizing -AV information such as (Z)ip-extra should be used with this in mind. When a new PKZIP is released, the PCBFiler-mode (D)elete command should not be used until PCBFV can be updated to handle new -AV stamps or until Yandell Computer Services announces no updates to PCBFV are needed. 5.8 Revision history --------------------- Date Version Details -------- ------- ------- 07-19-90 1.0 PCBFV first released. 08-02-90 1.1 Added wildcard (R)ead ability, ability to use one PCBFV.CNF file for multi-node systems, at the "More?" prompt the percentage of the text file that has been read is displayed. 10-19-90 2.0 See the enclosed file FEATURES.NEW. 11-21-90 2.1 " " " " " 02-22-91 2.2 " " " " " 04-26-91 2.3 " " " " " 07-19-91 2.4 " " " " " 08-24-91 2.45 " " " " " 12-20-91 2.5 " " " " " 07-31-92 3.0 " " " " " 11-27-92 3.1 " " " " " 01-09-93 3.2 " " " " " 01-29-93 3.3 " " " " " -------------------------------------------------------------------- Page 29 PCBFV Page 29 -------------------------------------------------------------------- 6.0 Registering PCBFV ---------------------- PCBFV is not free software. PCBFV should be registered no later than 30 days after installation. Registration is $15.00 and may be paid by check, money order, VISA, Mastercard or American Express. If using a charge card, you will receive a registration number INSTANTLY! Refer to the enclosed file ORDER.FRM for complete registration instructions. 6.1 Register with CONFIDENCE - Author Information -------------------------------------------------- L. Brent Yandell has been programming for over eleven years, including more than five years of developing telecommunications software. Many Sysops will be familiar with ChatBox, the popular on- line PCBoard chat door, and QReader, the `full-screen' text door. Yandell Computer Services (YCS) is a licensed business, operating and existing under the laws of the State of Florida. Writing BBS Shareware doors and utilities, in addition to custom programming, is our business.... our ONLY business. First Door Release: 7/6/87 (USBBSDOR) - Still updated and supported! YCS Shareware is GUARANTEED (each product's documentation contains each product's specific guarantee). Yandell Computer Services is an *AUTHORIZED* merchant for VISA, Mastercard and American Express charge cards. A dedicated multi-node BBS for support and on-line registrations, a toll-free voice line for registrations, and a voice support line for registered customers are just a few of our offerings in our efforts to provide you with FAST, FRIENDLY SERVICE.